N-tier architecture for a casino management system and method

ABSTRACT

The present invention provides a system and method for gaming system configuration and control in a gaming environment. Certain embodiments include receiving a request for an application to execute at a gaming system, and routing the request to an appropriate application server to provide the application at the gaming system. The request may be routed based on a status of a plurality of application servers, for example. The method may also include verifying that the gaming system is authorized to execute the application. In an embodiment, the method includes distributing a request for data among a plurality of database servers. The method may further include updating an application at the gaming system prior to execution of the application. In an embodiment, the application is automatically updated prior to execution. The method may also include detecting alteration of an application prior to execution of the application.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.10/935,514, filed Sep. 7, 2004, which is related to, and claims priorityfrom, U.S. Provisional Application No. 60/501,098, filed on Sep. 8,2003, with inventors Gary Frerking, Phillip Blanton, Lattamore Osburn,Jeff Topham, Robert DelRossi, and Kent Reisdorph, and entitled “ThreeTier Architecture for Casino Management System.”

BACKGROUND OF THE INVENTION

The present invention generally relates to a gaming system network. Inparticular, the present invention relates to a configuration and controlsystem that allows one or more gaming systems to dynamically requestapplications and/or services from one or more servers.

Gaming machines, such as slot machines, fruit machines, or pokermachines, have in recent years become one of the more popular, exciting,and sophisticated wagering activities available at casinos and othergambling locations. At the same time, gaming machines have also become asource of greater revenue for gaming establishments. Thus, competitionbetween manufacturers of gaming machines has intensified as competitorsvie for business from gaming establishments.

A gaming machine providing entertaining and enticing features forplayers would be highly desirable to attract both new and returningplayers to a gaming establishment. Additionally, a gaming machine thatallows customization and dynamic modification by an operator would behighly desirable to provide new features to customers.

Current gaming machines are difficult to reconfigure and offer the samegame to multiple users at multiple gaming establishments. Certain gamesmay become old or unattractive to players and need updating orreplacing. Changing a gaming machine to a different game or formatinvolves time-consuming and difficult procedures by an operator. Thus,an improved system and method for updating or replacing games or otherapplications on a gaming machine or other gaming system would be highlydesirable.

Additionally, configuration of a gaming machine by an operator raisesconcerns regarding security of data and integrity of a game on thegaming machine. That is, gaming establishments and legal authoritiesplace high priority on the integrity of a game, such as a slot or pokergame. Thus, there is a need for a configurable system that does notdisturb sensitive game or prize data.

Current systems are often susceptible to reduced performance during peakperiods of activity caused by overburdened servers providingapplications to gaming machines or gaming workstations. Additionally,failures in current gaming environments often lead to play stoppage orother gaming problems. Casinos and other gaming establishments seek toavoid such delays and system failures to maintain player enjoyment andencourage repeated play and repeated visits. Thus, a system and methodthat improves gaming reliability and efficiency would be highlydesirable.

Thus, there is a need for a configuration and control system and methodfor a gaming environment that allows one or more gaming systems todynamically request applications and/or services from one or moreservers.

BRIEF SUMMARY OF THE INVENTION

The present invention provides a system and method for a configurablegaming system. Certain embodiments provide an improved gaming networkfor providing applications to one or more gaming systems. The gamingnetwork includes a plurality of application servers servicing requestsfrom at least one gaming system and a load balancer distributingrequests from the at least one gaming system among the plurality ofapplication servers. The application servers may host a plurality ofapplications and/or web services for the gaming system(s).

In an embodiment, the application servers include a multi-tieredarchitecture. The multi-tiered architecture may include an applicationprogramming interface, at least one application, an operating system,and/or a data access interface layer, for example. The plurality ofapplication servers may transmit information to the gaming system(s)that are subscribed to the plurality of application servers. In anembodiment, the application servers include different applications. Inan embodiment, the application server(s) respond to a request if thegaming system(s) bear a valid license token for the requestedapplication and/or service. The plurality of application servers mayprovide local live update of one or more applications on one or more ofthe plurality of application servers.

In an embodiment, the load balancer distributes the requests based on astatus of the plurality of application servers. The system may furtherinclude a database server storing data for retrieval by the plurality ofapplication servers. The load balancer may balance requests among aplurality of database servers. A request from a gaming system mayinclude a request for a downloadable game, for example.

Certain embodiments provide an updatable gaming network including anapplication server servicing requests from at least one gaming system,where the application server includes a local live update applicationfor updating an application on the application server. The local liveupdate application may automatically update one or more applications onthe application server. The local live update application may update anapplication on the application server at execution of the application.

The updatable gaming network may also include a stub/loader running at agaming system, where stub/loader queries the local live updateapplication to update an application to be executed at the gamingsystem. The stub/loader may detect alteration of an application prior toan execution of the application. The stub/loader may detect alterationof the application in conjunction with the local live updateapplication. In an embodiment, the stub/loader verifies the applicationand stores an indication of verification of the application. Thestub/loader may verify a license for use of the application at thegaming system.

In an embodiment, the gaming network also includes a load balancerdistributing requests from the gaming system(s) among a plurality ofapplication servers. The load balancer may balance requests among aplurality of database servers. The network may also include a databaseserver storing data for retrieval by the application server. In anembodiment, the application includes a downloadable game, for example.

Certain embodiments provide a method for gaming system control in agaming environment including receiving a request for an application toexecute at a gaming system, and routing the request to an appropriateapplication server to provide the application at the gaming system. Therequest may be routed based on a status of a plurality of applicationservers, for example.

The method may also include verifying that the gaming system isauthorized to execute the application. In an embodiment, the methodincludes distributing a request for data among a plurality of databaseservers. The method may further include updating an application at thegaming system prior to execution of the application. In an embodiment,the application is automatically updated prior to execution. The methodmay also include detecting alteration of an application prior toexecution of the application.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an embodiment of a casino management systemin accordance with an embodiment of the present invention.

FIG. 2 is a block diagram of an embodiment of a portion of the casinomanagement system of FIG. 1 in accordance with an embodiment of thepresent invention.

FIG. 3 is a block diagram of an embodiment of a portion of the casinomanagement system of FIG. 1 in accordance with an embodiment of thepresent invention.

FIG. 4 is a block diagram of an embodiment of a portion of the casinomanagement system of FIG. 1 in accordance with an embodiment of thepresent invention.

FIG. 5 is a block diagram of an embodiment of a portion of the casinomanagement system of FIG. 1 in accordance with an embodiment of thepresent invention.

FIG. 6 is a block diagram of an embodiment of a portion of the casinomanagement system of FIG. 1 in accordance with an embodiment of thepresent invention.

FIG. 7 is a flow diagram for a method for satisfying execution requestsin accordance with an embodiment of the present invention.

DESCRIPTION OF THE INVENTION

Referring to FIG. 1, a casino network system 11 includes a plurality ofgaming machines 13, 15, and 17 interconnected across a network 19 to anapplications server 21. Applications server 21 is connected to adatabase server 23 via a communication link 25 which is separate fromnetwork 19.

System 11 also includes a casino workstation 31 connected to network 19.In addition, one or more external systems 33, for example workstationsfrom remote casinos, may be connected to network 19.

Gaming machines 13, 15, 17, workstation 31 and external systems 33utilize the applications or web services of application server 21. Inaddition, gaming machines 13, 15, 17, workstation 31 and externalsystems 33 may communicate with one another via network 19 usingstandard protocols. Communication between a gaming machine and network19 may occur with or without a smart communications interface, forexample. However, database server 23 can only be accessed viacommunication link 25.

Communication link 25 is a high speed data link, and providesconsiderably faster communication than that across network 19. Link 25may be formed from fiber optic cabling using lower layer protocols suchas 100BASE-T, Gigabit Ethernet, and FDDI (fiber distributed datainterface).

Referring to FIG. 2, each gaming machine 13, 15, 17 includes a smartcommunications interface (SCI) 101, 103, 105, respectively, whichcommunicates with a respective game controller 107, 109, 111 using aparticular protocol, for example, a Slot Accounting System (SAS)protocol, a Slot Data System (SDS) protocol, or other protocol. SCI 101communicates directly onto network 19, whereas SCI's 103, 105communicate through a data port unit (DPU) 113 and a poller 115, in theparticular embodiment of FIG. 2. In another embodiment, a gamecontroller may incorporate SCI functionality and communicate directlywith network 19.

DPU 113 continually polls SCI's 103, 105 along lines 121, 123,respectively. DPU 113 may communicate with other gaming machines (notshown) via one or more lines 125. Each SCI 103, 105 collects data fromits associated game controller and then buffers the data fortransmission to DPU 113. Communication between SCIs 103, 105 and DPU 113may use an RS485 serial communication standard, for example.

Poller 115 communicates with DPU 113 along line 114. Poller 115 maycommunicate with other DPUs (not shown) via one or more lines 116.Poller 115 communicates with an addressed DPU 113, sending informationto DPU 113 as well as retrieving information buffered by DPU 113.Polling by poller 115 occurs in a serial protocol fashion. Poller 115communicates with one DPU 113 at a time. Each DPU 113 listens for apolling message from poller 115. When poller 115 has obtained data froma DPU 113, poller 115 packages the data and places it onto network 19.

In an embodiment, SCI 101 is not polled. Instead SCI 101 placesinformation directly onto network 19. SCI 101 retrieves data from gamecontroller 107 and transmits said data across network 19 to adestination specified by SCI 101. For example, when the protocol messageof controller 107 indicates a meter change, SCI 101 reads the meter dataand determines the meter change. SCI 101 then packages the data forplacement onto network 19.

When SCI 103 retrieves data from game controller 109, for example, billdata indicating that a $50.00 bill has been inserted into the gamingmachine's bill accepter, the bill data is stored in the buffer memory ofSCI 103. After transmission of the bill data to SCI 103, the data iserased from or allowed to be overwritten in the buffer memory ofcontroller 109.

DPU 113 then polls SCI 103 and the bill data is sent to DPU 113.However, SCI 103 does not immediately delete the bill data from itsbuffer memory in response to sending the data. DPU 113 stores thereceived bill data in its buffer memory. Thereafter, DPU 113 sends aconfirmation signal to SCI 103 indicating that DPU 113 has successfullyretrieved and stored the bill data. In response to receiving theconfirmation signal, SCI 103 erases the bill data from its buffer memory(or allows the memory space to be overwritten with new data). Thisprocedure guarantees delivery of data.

Poller 115 then polls DPU 113 and the bill data is next sent to poller115. However, the DPU 113 does not immediately delete the data from itsbuffer memory in response to sending the data to poller 115. Poller 115stores the received bill data in buffer memory. Thereafter, Poller 115sends a confirmation signal to DPU 113 indicating that poller 115 hassuccessfully retrieved and stored the data. In response to receiving theconfirmation signal, DPU 113 erases the data from its buffer memory (orallows the memory space to be overwritten with new data). Poller 115packages the data and places it onto network 19. Alternatively, theconfirmation signal which is sent to DPU 113 may be sent after the datais written to a local disk (not shown) or to database 45.

Referring again to FIG. 1, applications server 21 is designed to be runon a network platform and to service requests from gaming machines 13,15, 17, as well as from workstation 31 or external systems 33. Casinonetwork system 11 provides a network environment in which, for example,Microsoft Corporation's .NET™ framework is used. Applications server 21hosts various applications or web services that may be accessed fromnetwork 19, through standard protocols, such as XML (extensible markuplanguage), SOAP (simple object access protocol), WAP (wirelessapplication protocol), HTTP (hypertext transport protocol), SMTP (simplemail transfer protocol), etc.

Applications server 21 has a multi-tiered architecture that includes anumber of software layers including one or more applications 35, anapplication program interface (API) 37, an operating system (OpSys) 39,and a data access interface layer 47. Applications 35 provide a numberof different services, including accounting services, player trackingservices, progressive game services, browsing services, cashless playservices, etc. Applications 35 may be written in various languagesincluding, for example, C#. Operating system 39, for example, is aWindows® brand operating system which provides conventional functions.

Applications server 21 can push out, i.e., publish, information tovarious subscribers including but not limited to gaming machines 13, 15,17, workstation 31 or external systems 33. Likewise, poller 115 (FIG. 2)could be a subscriber for receiving information from applications server21.

For example, applications server 21 may learn that a jackpot event hasoccurred. Server 21 then publishes that information to workstation 31,or for example, to a jackpot server (not shown). Workstation 31subscribes to this jackpot notification service by a communicationrequest sent over network 19 to applications server 21. The request asksserver 21 to notify the specific workstation 31 whenever a jackpot eventoccurs. Workstation 31 makes use of this notification, for example, by(1) notifying casino personnel that a jackpot has occurred, (2)determining whether a jackpot fill of the particular gaming machine 13is required, etc.

As another example, gaming machine 13 may subscribe to a “bonus time”alert. Applications server 21 notifies gaming machines that havesubscribed that a bonus period has started and that jackpots are to bepaid out at twice the pay table, for example. This bonusing service forparticular gaming machines can be subscribed to, for example, usingcasino workstation 31. Workstation 31 may communicate a request toapplications server 21 to publish to specifically-identified gamingmachines that a bonus period is to begin. The request may also provideadditional information as to the amount of the bonus, the type of bonus,a bonus multiplier, etc. The request may also ask server 21 to publishthe end of the bonus period as well. The applications server 21 mayprovide such a bonus service in real time with the bonus event, ormerely provide a scheduled command for future bonus events.

In another example, applications server 21 may publish to certain gamingmachines that a tournament has ended. Using the method taught in U.S.Pat. No. 6,039,648, assigned to Casino Data Systems, server 21 maycommunicate the end of a tournament play, so that appropriate pay tablesand displays at the gaming machines may be activated.

API 37 includes a plurality of functions that can be called by othersystems or devices connected to network 19. Such functions includeconventional method or function calls as well as remote calls, e.g.,proxy and SOAP/XML invocations. For example, API 37 may be called byslot machines 13, 15, 17. Also workstation 31 includes softwareapplications 55 which when executed make calls to API 37. Likewise,applications on external systems 33 are able to use the functions of API37 by presenting calls over network 19.

For example, API 37 processes a publication request. Meter data isreceived by applications server 21 which indicates that a jackpot hasoccurred. API 37 stores the meter data and then publishes the data toall subscribers.

In another example, external system 33 may be a news reporting serverlocated at an internet e-mail address. The news reporting server mayrequest notification of all jackpot events that exceed $1,000,000.00.

Referring again to FIG. 1, database server 23 is a relational databaseserver, for example, a Microsoft® Structured Query Language (SQL)server, or an Oracle® database server, or the like. Database server 23includes a database (DB) 45 and software 53 which is executed to handlerequests for particular services. The request is made by applicationsserver 21 and typically the service requested is to provide data to orretrieve data from database 45. Examples of services provided bydatabase server 23 include (1) database storage of gaming activity,player account information, advertisements, ticketing, etc. and (2)database retrieval of player information, accounting data, applicationprograms, etc.

Data access interface 47 is a database access technology, for example,Microsoft's® ADO.NET software. Data access interface layer 47 interfaceswith database server 23 to perform various tasks, for example,retrieving data from database server 23 in cached form.

Interface 47 provides SQL queries to execute stored procedures insoftware 53. For example, a fill procedure is called to fill a data setwith data from database 45. The data set serves as a container thatstores the data from database 45 in a cached form. The data set istransferred to applications server 21, and the server 21 is thendisconnected from database server 23.

Referring to FIG. 3, other application servers, for example applicationsserver 49, may be added to network 19 to service additional gamingmachines as more and more gaming machines are added to system 11.Applications server 49 may likewise service casino workstation 31 (FIG.1), external systems 33 (FIG. 1) and gaming machines 13, 15, 17 (FIG.1), for example.

Applications server 49 is connected to database server 23 viacommunication link 25. Connections to database server 23 are made andbroken, as requested data is cached for use by the particularapplications servers 21, 49 requesting the data.

As shown in FIG. 3, a load balancer 20 may be connected betweenapplications servers 21, 49 and network 19. Load balancer 20 shares theworkload between applications server 21 and applications server 49. Whena service request is received by load balancer 20, balancer 20distributes the request to either applications server 21 or 49 asappropriate. If applications server 21 is turned OFF, or incorrectlydrops out of the system, load balancer 20 makes use of applicationserver 49 instead. The other network components are blind to the numberof applications servers which are providing services. Each applicationsserver 21, 49 may contain identical applications 35 to enable loadbalancing. More than one load balancer 20 may provide additional systemredundancy and scaling.

Alternatively, poller 115 (FIG. 1), for example, may identify thespecific applications server (21 or 49) which is to service the poller'srequest.

API 37 of applications server 21 may respond to a request only if therequest bears a valid license token. Thus, an unauthorized externalsystem 33 (FIG. 1) would be prevented from seeking services fromapplications server 21 without such a token.

Referring to FIG. 4, a licensing server 61 may be connected to network19 for supplying license tokens. Workstation 31 places a service requestonto network 19, which is received by licensing server 61. Licensingserver 61 responds back to workstation 31 providing a license token toworkstation 31 for the particular service request. Workstation 31attaches the license token to its request and places the request andtoken onto the network for receipt by applications server 21.

As an example, a casino may be licensed such that ten (10) jackpot fillclient applications may receive services from applications server 21.When the eleventh jackpot fill client application begins requestinglicense tokens from server 61, that event is noticed by licensing server61. One option for responding to this unlicensed situation is to providethe license token, but store this event in memory for subsequentretrieval by a service technician of the systems company. Uponretrieval, the technician will note that the casino needs to be licensedfor the eleventh jackpot fill client application and then informs thecasino management accordingly. Another option for server 61 respondingto this unlicensed situation is not to provide the license token.

In an embodiment, licensing server 61 may be used to enable or disablefeatures or behaviors according to jurisdictional regulatoryrequirements. As an example, application 55 on workstation 31 mayrequest services related to harm minimization. Licensing server 61 mayrefuse a license token in jurisdictions that do not use harmminimization functionality. As another example, application 55 onworkstation 31 may request services with jurisdiction-specific behavior,such as services related to ticket expiration. The license tokenprovided by licensing server 61 may include jurisdiction-specificlicensing information to enforce such behavioral requirements.

In addition, the owner of the casino system 11 may have a number ofsuppliers which are authorized (licensed) to gain access and obtainservices from applications server 21. Those suppliers may be registeredon license server 61 so that tokens will be dispensed to the listedsupplier.

As will suggest itself, the functions of license server 61 may becarried out by an application 35 of applications server 21. In such anevent, a separate server 61 is not utilized.

To provide security to system 11, encryption may be provided throughoutthe system, although encryption may be unnecessary for communication onlink 25. In addition, licensing server 61 may include a hardware key 63,e.g., a USB “dongle plug”. Hardware key 63 is removably pluggable intolicensing server 61. When the hardware key 63 is removed from server 61,server 61 may not be modified or changed. Alternatively, the hardwarekey 63 may contain licensing information such that if the key 63 isremoved, server 61 may no longer be capable of issuing licenses toapplications that are subsequently launched. Similarly, a hardware key65 may be provided in workstation 31 and a hardware key 67 may beprovided at an external system 33.

Referring to FIG. 5, applications server 21 accesses data primarily fromdatabase server 23. However, one or more other data providers 51 may beconnected to communication link 25 in order to permit access byapplications servers 21 (as well as server 49, shown in FIG. 3). A dataprovider 51 may be a second database server similar to server 23, or aremote casino network system, or a third party web service, or anexternal vendor system. For example, a casino employee at workstation 31may request information as to the availability of a hotel room from athird party database server 51.

Where an additional database server 51 is added to system 11, forexample to scale out the system, a load balancer, similar to balancer20, may be disposed between applications server 21 and database servers23, 51. In such a case, a cluster fault tolerant database solution maybe used such that applications server 21 is blind as to the number ofdatabase servers it is accessing.

Referring to FIG. 6, casino workstation 31 includes a number ofapplications 55. From time to time, one of applications 55 may need tobe updated by a new version of the software which forms the application55. A Local-Live-Update software application (“LLU”) 601 on applicationsserver 21 updates the software applications 55. This takes place by LLU601 downloading a fresh copy of the files associated with application 55to workstation 31. The files may include the executable image ofapplication 55 itself as well as any supporting files used byapplication 55 including but not limited to executable modules,configuration files, stored procedures, data files, help files, imagefiles and the like. The fresh application files are retrieved fromdatabase 45. Alternatively, instead of placing the fresh applicationfiles in database 45, the files may be stored in separate memory, i.e.,an application repository comprised of a hierarchy of file systemfolders, for example, separate from database server 23.

An application 55 may be updated, for example, in response toworkstation 31 making a specific request to applications server 21 toprovide an update. Alternatively, LLU 601 may automatically provide thesoftware update without request from workstation 31. The automaticupdate may occur at a scheduled time, e.g., midnight on the last day ofeach month. Also, LLU 601 may update an application 55 each time theapplication 55 is to be run. LLU 601 may provide similar applicationupdate services to any system or workstation accessible via network 19or communication link 25 including, for example, gaming machines 13, 15,17, and external systems 33 of FIG. 1.

In an embodiment, LLU 601 may facilitate web-based applicationdeployment from a web server to a gaming system, such as workstation 31and/or gaming machine 13, 15, 17 (FIG. 1). Web-based gamingapplications, services, and/or customized interfaces may be downloadedto and/or executed on the gaming system via LLU 601.

In an embodiment, application deployment does not interfere with adependent application's normal operation and proceeds in a pseudoplatform-independent fashion. Additionally, LLU 601 may validate file(s)against known good files when an application is launched to determine ifa file should be replaced and/or updated.

In an embodiment, LLU 601 provides password protection or otherauthentication method to prevent unauthorized access to clientapplications. The LLU 601 may validate each application file against aknown good file when the application is launched to prevent people fromediting an application's file and running the application in an unknownstate. To prevent a bypassing of the system, the LLU 601 may create amutual exclusion object (MUTEX) which allows multiple applicationthreads to share a common resource but not simultaneously. Thus, eachclient checks the MUTEX upon initialization to determine if anapplication may be accessed.

In addition, an application 55 or any of its supporting files may bedownloaded from applications server 21 because the particularapplication 55 on workstation 31 has been altered or because sometampering has occurred with the software. For example, when a particularapplication 55 is to be run on workstation 31, the alteration isdetected, and the fresh application files are then downloaded.

The detection of the altered files associated with application 55 occursat the time that the application 55 is to be launched. A stub/loaderapplication 603 is run on workstation 31 prior to each launching of anapplication 55. Stub/loader application 603 controls the launching ofall client applications 55 on workstation 31. When stub/loader 603 isstarted, it queries the web service LLU 601 of applications server 21for details of the particular application 55 which is to be launched.Stub/loader 603: (1) examines the local directory structure of theto-be-launched application 55, (2) determines the presence of each ofthe files of the to-be-launched application 55, (3) installs or updateseach file as needed, and (4) launches the executable of theto-be-launched application 55.

For example, stub/loader 603 queries LLU 601 for the directories of eachof the application's files. The LLU 601 returns to stub/loader 603 adata structure containing the directory names and hierarchy. Thestub/loader 603 then compares the information in the returned datastructure with the existing directories of the to-be-launchedapplication 55.

Stub/loader 603 also queries LLU 601 for the file names of each of theto-be-launched application's dependent files. Stub/loader 603 comparesthe returned file names with the names of the files in theto-be-launched application 55.

Stub/loader 603 also queries LLU 601 for a hash value, such as an MD5Hash value, for a specific file. LLU 601 does not hash the file; rather,the file is hashed at the time the file is added to the system. The hashvalue is stored in database 45 or other suitable location such ashardware key 63 associated with licensing server 61 (FIG. 4).Stub/loader 603 compares the returned hash value with the hash valueobtained by the stub/loader hashing the file in the to-be-launchedapplication 55. Using an MD5 hash routine, for example, stub/loader 603inspects each file in the to-be-launched application 55.

Stub/loader 603 may also query LLU 601 for other details and informationof the to-be-launched application, such as data related to the date andtime the file was created, data related to when the file was lastmodified, etc. Stub/loader 603 may use this information to inspect theto-be-launched application 55 and its associated files. Otherinformation that may be used includes, for example, the size in bytes ofthe specified file.

After inspecting the to-be-launched application with the information anddata supplied by LLU 601, stub/loader 603 determines whether to installa new file, or replace an outdated file. In response to itsdetermination that a new file is necessary or desired, stub/loader 603queries LLU 601 for a data structure containing the entire file.Stub/loader 603 creates a file, writes the returned data structure intothe file and dumps the file to the disk of workstation 31.

Once stub/loader 603 has updated the to-be-launched application,stub/loader 603 queries LLU 601 for the file name of the to-be-launchedapplication's executable file. Upon return of the executable file'sname, stub/loader 603 launches the executable file.

The stub/loader application 603 stores a unique identifier into memory605 to indicate that the application 55 has been approved. Whenapplication 55 is finally launched, the application 55 looks for theunique identifier in memory 605. If it is found, the identifier iserased from memory 605, and the application 55 is launched. If theunique identifier is not found in memory 605, indicating that theapplication 55 has not been approved, the application 55 is notlaunched.

In addition to verifying that application 55 has not been altered, thestub/loader application 603 may also verify that there is a license topermit use of the application 55. Stub/loader 603 requests this servicefrom licensing server 61 (FIG. 4).

As shown in FIG. 6, a casino administrator station 607 is connected tonetwork 19. Station 607 is used by authorized personnel to install newapplications and updates to the system, and to remove old applications.

For example, station 607 includes an administrator application 609 whichqueries LLU 601 to add new files to database 45 or to update existingfiles in database 45. Administrator application 609 transmits new filedata to LLU 601 with a request to install or update a specified file ina specified application. In addition, administrator application 609 may(1) add a new application record to the database 45, (2) update thedetails of a specified application, (3) remove a specified file fromdatabase 45 and (4) remove a specified application and all of its filesfrom database 45. Also, administrator application 609 may obtaininformation from database 45, as for example, (1) a data structurecontaining the file name of each of a specified application's files, (2)a data structure containing the details of a specified application, (3)a data structure containing the name of each application stored indatabase 45, (4) a data structure containing all of the information on aspecified file, and (5) the number of files which belong to a specifiedapplication.

It is anticipated that regulatory requirements may dictate specialaccess control for sensitive portions of casino network system 11 suchas station 607. Examples of special access control may include but arenot limited to locating station 607 in a physically secure and monitoredroom, requiring biometric identification, or requiring more than oneauthorized employee to be present in order to access system 607. It isfurther anticipated that casino network system 11 may be adapted asnecessary to meet such regulatory requirements.

For purposes of simplicity, only three gaming machines 13, 15, 17 areshown in FIG. 1. In actuality, a casino may contain hundreds, or eventhousands, of gaming machines. In addition to gaming machines, a casinomay include various non-gaming machine locations, such as craps andblackjack. Such locations may include an SCI, similar to SCI 101 or 103,which is connected to network 19.

Each gaming machine will require its own particular services fromapplication server 21. For example, some but not all gaming machineswill be included in a progressive game and thus require a progressiveservice from applications server 21. Typically, all gaming machines willrequire an accounting service from server 21 which will account forcoins and bills inserted into the gaming machine as well as anaccounting of coins cashed out of the gaming machine to the player.

Other services, such as player tracking and cashless play services, canbe provided by server 21. A typical player account may be stored indatabase 45 for tracking of the player. The player accounts are updatedby server 21 as player information is sent to server 21 from gamingmachines 13, 15, 17, workstation 31 or an external system 33. Forexample, a restaurant acting as an external system 33 may request server21 to add loyalty points to the player's account in database 45 based onthe amount of money spent by the player at the restaurant. As anotherexample, a player at gaming machine 13 may request applications server21 to convert 1000 points of the points balance in the player's accountto credits on the credit meter of gaming machine 13. As another example,applications server 21 may provide game programs or other parameters toa particular gaming machine.

More specifically, gaming machine 13 sends a service request toapplications server 21. SCI 101 (FIG. 2) packages the request in aproper protocol and places the request onto network 19. Various switchesand/or routers may be included in network 19 in order to route theservice request to applications server 21. The request may include (1)data, (2) a message request, and (3) the network address of applicationsserver 21. The message request seeks a particular service to beperformed by execution of an application 35. Application 35 is run inconnection with the data, if any, in the request. Application 35, ifrequired, then generates a message back onto network 19 addressed tomachine 13. SCI 101 (FIG. 2) receives the message and respondsaccordingly, as for example, adjusting the credit meter, generating adisplay of information to the player, etc.

Alternatively, SCI 101 or 103 may be connected to a hub for wirelesscommunication of the service request to the network 19. The servicerequest is received by the hub, repackaged and then broadcast to areceiving device that is connected to the network. The receiving devicepackages the service request and places the service request onto thenetwork.

Thus, as described above, certain embodiments facilitate execution ofrequests from gaming systems in a gaming environment. FIG. 7 is a flowdiagram for a method 700 for satisfying execution requests in accordancewith an embodiment of the present invention. First, at step 710, arequest workload is identified. That is, a number of requests forapplications and/or data from one or more gaming systems in a gamingenvironment, such as a casino, is determined. Then, at step 720, anumber of available servers is identified. For example, server workloadand applications and/or data available on each server may be determined.

Next, at step 730, pending request(s) are routed to one or more serversable to handle the request(s). For example, data requests are routed toappropriate data servers, and application requests are routed toappropriate application servers. Optionally, at step 740, a license orlicense token, for example, may be authenticated to verify that arequesting system is authorized to access a server, application, and/ordata. In an embodiment, at step 750, a server responding to a requestmay optionally determine if an update to a requested application and/ordata is appropriate. For example, as described above, a server mayverify application integrity and/or check for an updated version of theapplication and install a corrected/updated version of the applicationbefore execution of the application for the requesting gaming system.Then, at step 760, requests are fulfilled by appropriate server(s).

Thus, certain embodiments of the present invention provide a loadbalancing system for a gaming environment. Certain embodiments provide asystem and method for local live update of applications in a gamingenvironment. Certain embodiments facilitate web-based deployment ofapplications and services independent of gaming system platform.Applications may be validated for proper license and/or file integrityprior to execution and/or download.

Certain embodiments simplify application update cycles and ensure thatall client systems in a gaming environment may be using the same versionof an application. Certain embodiments provide for easy applicationroll-back in the event of a bad application release or other error.Certain embodiments minimize support and maintenance through loadsharing, redundancy, and updatability. Certain embodiments prevent anapplication from running in an unknown or erroneous state.

While the invention has been described with reference to one or morepreferred embodiments, those skilled in the art will understand thatchanges may be made and equivalents may be substituted without departingfrom the scope of the invention. In addition, many modifications may bemade to adapt a particular step, structure, or material to the teachingsof the invention without departing from its scope. Therefore, it isintended that the invention not be limited to the particular embodimentdisclosed, but that the invention will include all embodiments fallingwithin the scope of this application.

1. An improved gaming network for providing applications to one or moregaming systems, said gaming network comprising: a plurality ofapplication servers servicing application requests from at least onegaming system, wherein each of said plurality of application serversincludes a multi-tiered architecture having a plurality of softwarelayers; and a load balancer automatically distributing applicationrequests from said at least one gaming system among said plurality ofapplication servers.
 2. The gaming network of claim 1, wherein saidplurality of application servers host a plurality of applications or webservices for said at least one gaming system.
 3. The gaming network ofclaim 1, wherein said multi-tiered architecture includes at least one ofan application programming interface, at least one application, anoperating system, and a data access interface layer.
 4. The gamingnetwork of claim 1, wherein said plurality of application serverstransmit information to said at least one gaming system subscribed tosaid plurality of application servers.
 5. The gaming network of claim 1,wherein application servers within said plurality of application serversinclude different applications.
 6. The gaming network of claim 1,wherein said plurality of application servers respond to said request ifsaid at least one gaming system bears a valid license token.
 7. Thegaming network of claim 1, wherein said plurality of application serversprovide local live update of one or more applications on one or more ofsaid plurality of application servers.
 8. The gaming network of claim 1,wherein said load balancer distributes said requests based on a statusof said plurality of application servers.
 9. The gaming network of claim1, further comprising a database server storing data for retrieval bysaid plurality of application servers.
 10. The gaming network of claim9, wherein said load balancer balances requests among a plurality ofdatabase servers.
 11. The system of claim 1, wherein request comprises arequest for a downloadable game.
 12. An updatable gaming network, saidgaming network comprising: an application server servicing requests fromat least one gaming system, said application server including a locallive update application for automatically updating and validating anapplication on said application server, wherein said application serverincludes a multi-tiered architecture having a plurality of softwarelayers.
 13. The gaming network of claim 12, wherein said local liveupdate application automatically updates one or more applications onsaid application server.
 14. The gaming network of claim 12, whereinsaid local live update application updates an application on saidapplication server at execution of said application.
 15. The gamingnetwork of claim 12, further comprising a stub/loader running at agaming system, said stub/loader querying said local live updateapplication to update an application to be executed at said gamingsystem.
 16. The gaming network of claim 15, wherein said stub/loaderdetects alteration of an application prior to an execution of saidapplication.
 17. The gaming network of claim 16, wherein saidstub/loader detects alteration of said application in conjunction withsaid local live update application.
 18. The gaming network of claim 15,wherein said stub/loader verifies said application and stores anindication of verification of said application.
 19. The gaming networkof claim 15, wherein said stub/loader verifies a license for use of saidapplication at said gaming system.
 20. The gaming network of claim 12,further comprising a load balancer automatically distributing requestsfrom said at least one gaming system among a plurality of applicationservers.
 21. The gaming network of claim 20, wherein said load balancerbalances requests among a plurality of database servers.
 22. The gamingnetwork of claim 12, further comprising a database server storing datafor retrieval by said application server.
 23. The gaming network ofclaim 12, wherein said application comprises a downloadable game.
 24. Amethod for gaming system control in a gaming environment, said methodcomprising: receiving a request for an application to execute at agaming system; and automatically routing said request to an appropriatemulti-tiered application server to provide said application at saidgaming system.
 25. The method of claim 24, further comprising verifyingthat said gaming system is authorized to execute said application. 26.The method of claim 24, wherein said request is routed based on a statusof a plurality of application servers.
 27. The method of claim 24,further comprising distributing a request for data among a plurality ofdatabase servers.
 28. The method of claim 24, further comprisingupdating an application at said gaming system prior to execution of saidapplication.
 29. The method of claim 28, wherein said updating stepfurther comprises automatically updating said application.
 30. Themethod of claim 24, further comprising detecting alteration of anapplication prior to execution of said application.